LTE Gateways For Home And Commercial Sensor Data

ABSTRACT

Aspects of the subject disclosure may include, for example, a device that receives data from a machine-type communication (MTC) device located at a premises, determines an identifier for the MTC device; compares the identifier with a list of identifiers; and, responsive to determining that the MTC device is a listed device, transmits the data to a first network element remote from the premises. The device and the first network element do not receive data from devices at the premises generating human traffic communications (HTC). The first network element transmits the data to a second network element for aggregation and subsequent transmission to a cloud data facility comprising cloud storage. A data path from the device to the first network element, from the first network element to the second network element, and from the second network element to the cloud data facility forms a secure data path. Other embodiments are disclosed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/228,636 filed on Aug. 4, 2016. All sections of the aforementionedapplication are incorporated herein by reference in their entirety.

FIELD OF THE DISCLOSURE

The subject disclosure relates to network elements for handling sensordata, and more particularly to gateways using long term evolution (LTE)technology for managing data from Internet of Things (IoT) devices inresidential and commercial environments.

BACKGROUND

A very wide variety of devices with differing device capabilities mayconnect to a communication network at various times and for variouspurposes (for example, a sensor periodically transmitting small amountsof data to a computing device). A network that includes such devices issometimes referred to as the “Internet of things” (IoT). IoT devices(also referred to herein as machine-type communication or MTC devices)are used in both residential and commercial settings. Residential IoTdevices can include smart appliances, smart thermostats,personal/medical monitors, alarm systems, etc. MTC devices are typicallysmall in size, with limited battery power and communication range. MTCdevices typically transmit data at lower power and limited bandwidthcompared with voice and data traffic generated by mobile communicationdevices of human users (sometimes referred to as human-typecommunications or HTC).

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 schematically illustrates device networks and access networks forresidential and commercial environments, in accordance with embodimentsof the disclosure;

FIG. 2 schematically illustrates HTC and MTC traffic from a residencebeing managed using LTE technology;

FIG. 3 schematically illustrates MTC sensor data traffic generated in aresidential environment and transmitted by an LTE gateway, in accordancewith an embodiment of the disclosure;

FIG. 4 schematically illustrates a cloud-based home residential datacenter for storing and monitoring MTC sensor data, in accordance with anembodiment of the disclosure;

FIG. 5 depicts an illustrative embodiment of a method used in portionsof the system described in FIGS. 1-4;

FIGS. 6-7 depict illustrative embodiments of systems that providecommunications services to LTE and MTC devices;

FIG. 8 depicts an illustrative embodiment of a web portal forinteracting with the communication systems of FIGS. 6-7;

FIG. 9 depicts an illustrative embodiment of a communication device; and

FIG. 10 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions, when executed, maycause the machine to perform any one or more of the methods describedherein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrativeembodiments for a device that facilitates performance of operations,comprising receiving data from a plurality of machine-type communication(MTC) devices located at a premises, where the device is located at thepremises; and transmitting the data as a MTC data flow to a networkelement remote from the premises, where the device does not receive datafrom user communication devices at the premises generating human trafficcommunications (HTC), and wherein the network element does not receiveHTC. The MTC data accordingly can be transmitted from the premises via asecure, dedicated MTC data path. Other embodiments are described in thesubject disclosure.

One or more aspects of the subject disclosure include a devicecomprising a processing system including a processor, and a memory thatstores executable instructions that, when executed by the processingsystem, facilitate performance of operations. The operations cancomprise receiving data from a machine-type communication (MTC) devicelocated at a premises, where the device and a plurality of MTC devicesare located at the premises; determining an identifier for the MTCdevice; comparing the identifier with a list of identifiers accessibleto the device; and, responsive to determining that the MTC device is alisted device based on the comparing, transmitting the data to a firstnetwork element remote from the premises; the first network element cancomprise a femtocell. According to aspects of the disclosure, the devicedoes not receive data from user communication devices at the premisesgenerating human traffic communications (HTC); the first network elementdoes not receive HTC; and the first network element transmits the datato a second network element for aggregation and subsequent transmissionto a cloud data facility comprising cloud storage. According toadditional aspects of the disclosure, a data path from the device to thefirst network element, from the first network element to the secondnetwork element, and from the second network element to the cloud datafacility comprises a secure data path.

One or more aspects of the subject disclosure include a machine-readablestorage medium, comprising executable instructions that, when executedby a processing system including a processor, facilitate performance ofoperations. The operations can comprise receiving data from amachine-type communication (MTC) device located at a premises; theprocessing system, a plurality of MTC devices, and a plurality of humantraffic communication (HTC) devices are located at the premises. Theoperations can also comprise determining an identifier for the MTCdevice; comparing the identifier with a list of identifiers coupled tothe processing system; and, responsive to determining that the MTCdevice is a listed device based on the comparing, transmitting the datato a first network element remote from the premises; the first networkelement can comprise a femtocell. According to aspects of thedisclosure, the processing system does not receive data from the HTCdevices; the first network element does not receive HTC data; and thefirst network element transmits the data to a second network element foraggregation and subsequent transmission to a cloud data facilitycomprising cloud storage. According to additional aspects of thedisclosure, a data path from the device to the first network element,from the first network element to the second network element, and fromthe second network element to the cloud data facility comprises a securedata path.

One or more aspects of the subject disclosure include a methodcomprising receiving, by a processing system comprising a processor,data from a machine-type communication (MTC) device located at apremises, where the processing system, a plurality of human-typecommunication (HTC) devices and a plurality of MTC devices are locatedat the premises. The method can further comprise determining anidentifier for the MTC device; comparing the identifier with a list ofidentifiers accessible to the processing system; and, responsive todetermining that the MTC device is a listed device based on thecomparing, transmitting the data to a first network element remote fromthe premises. According to additional aspects of the disclosure, theprocessing system does not receive data from the HTC devices; the firstnetwork element does not receive HTC; and the first network elementtransmits the data to a second network element for aggregation andsubsequent transmission to a cloud data facility comprising cloudstorage. According to additional aspects of the disclosure, a data pathfrom the processing system to the first network element, from the firstnetwork element to the second network element, and from the secondnetwork element to the cloud data facility comprises a secure pathdedicated to data from the MTC device.

Aspects of the disclosure relating to a residential environment arediscussed below. It will be appreciated that the disclosure can alsoapply to commercial or government facilities, e.g. nuclear facilities,correctional facilities, stores or other commercial enterprises.

FIG. 1 schematically illustrates a system 100 in accordance with anembodiment of the disclosure, including a device region 110, an accessnetwork 120, a core network 130 and the cloud 140. Device region 110 cancorrespond to all or part of a residence or a commercial building. Asshown in FIG. 1, device region 110 can include both MTC devices and HTCdevices and communicates with access network 120 using LTEcommunications.

In an embodiment, data from the MTC devices in a residence istransmitted to the access network separately from the HTC data, and ismanaged by a separate node of the access network. In this embodiment,data from the MTC devices is transmitted via LTE communications to anevolved UMTS Terrestrial Radio Access Network (E-UTRAN) Node B (eNodeB)that handles residential MTC traffic exclusively. In an embodiment, theeNodeB includes a femtocell. The MTC data is transmitted to a corenetwork 130 having a gateway function for home sensor data; the gatewayfunction causes the data to be stored in a Residential Data Center inthe cloud 140.

FIG. 2 schematically illustrates an arrangement 200 of residential MTCand HTC devices, in accordance with an embodiment of the disclosure. Inthis embodiment, residence 201 corresponds to the device domain 110shown in FIG. 1. A variety of devices are located within residence 201;the HTC devices 210 can include cell phones, tablets, personalcomputers, etc. for handling data generated by human users, particularlyvoice data. The MTC devices 220 can include a variety of environmentalsensors and other types of sensors, for example temperature/humiditymonitors, smoke detectors, motion detectors, cameras, etc.

The access network is shown schematically as base stations respectivelycorresponding to separate eNBs 250, 260. In this embodiment, the eNB 260is dedicated to receiving residential MTC traffic, and may be referredto as a Home eNode B (HeNB).

The MTC devices transmit data within the residence using a short-rangecommunication technology (e.g. Bluetooth®) to one or more Home LTE MTCgateways (H-LTE-MTC) dedicated to MTC data. In this embodiment, multipleH-LTE-MTC gateways 231, 232 are used to gather data from the MTCdevices, with each of the devices 220 being associated with a particulargateway. Alternatively, both gateways 231, 232 can be configured tocommunicate with all of the devices 200.

In this embodiment, the H-LTE-MTC gateways are located within theresidence and communicate with MTC devices that operate at a prescribedpower level (e.g. 100 mW or less) and are located within a prescribedrange of the gateway (e.g. 100 m or less).

In an embodiment, the MTC devices transmit data within the residenceusing a frequency band within, and substantially narrower than, thefrequency band used by the HTC devices. In another embodiment, the MTCdevices and HTC devices transmit in separate frequency bands.

FIG. 3 schematically illustrates an arrangement 300 of network elementsfor handling MTC data generated in a residence, in accordance with anembodiment of the disclosure. In this embodiment, sensor device 301generates data in the form of records 310, each record having a headerportion that includes an identifier 311 for the sensor device. Sensor301 transmits the data via short-range communications to H-LTE-MTCgateway 232. In an embodiment, gateway 232 is maintained in a low-poweror inactive state when not receiving data, and transitions to ahigh-power or active state when incoming data is detected.

Gateway 232 is dedicated to MTC traffic, and accordingly is configuredto accept only data generated by the MTC devices in the residence (or aspecified portion of those devices). In an embodiment, the gatewaydetermines the identifier 311 of the sending device from an arrivingrecord, and then compares that identifier with a list of MTC devices 235accessible by the gateway. In particular embodiments, list 235 ismaintained on a storage device that is integral with the gateway or thatis located in the residence and directly coupled to the gateway.

The list 235 of MTC devices can serve as a registry of MTC devices thatare approved for use on the premises. In a commercial environment, thiscan provide added security since only the approved devices have anyaccess to the LTE network.

In an embodiment, data from the MTC devices is temporarily stored at thegateway in a storage device 238. The data can be retained for apredetermined time period, and then sent as a bundle 320 to the Home eNB260 on the access network 140. In this embodiment, transmissions fromthe gateway 232 can be performed on a predetermined schedule. In anotherembodiment, the stored MTC data can be bundled and transmitted when apredetermined volume of data is reached, so that transmissions (databursts) from the gateway have a uniform size. In another embodiment, theMTC data is not stored at the gateway 232, so that the MTC data istransmitted as a data flow to the Home eNB.

FIG. 4 schematically illustrates an embodiment 400 in which MTC dataflows from the access network 120 to the core network 130 for storageand management in the cloud 140. In this embodiment, bundles of MTC data420 are transmitted from the access network 120 to a Home Gateway (HGW)401 on the core network 130. The HGW 401 can receive MTC data frommultiple H-LTE-MTC gateways located at multiple residences.

In this embodiment, the HGW is dedicated to receiving and processing MTCdata, and aggregates MTC data transmitted from a number of Home eNBdevices on the access network. In a particular embodiment, MTC data fromthe access network (for example, a data bundle transmitted from Home eNB260) is provided with a tag 421, enabling the HGW 401 to distinguish MTCdata from HTC data.

As shown schematically in FIG. 4, the aggregated MTC data is transmittedto a Home Residential Data Center 410 in the cloud 140. In thisembodiment, data center 410 includes a computing device 411 and astorage device 412. The data center can analyze and store the MTC datafrom a large number of residences. In a particular embodiment, the datacenter can arrange data generated by a particular type of sensor (e.g. ahumidity sensor) from numerous residences into a hierarchy (e.g. ageographical hierarchy), permitting analysis of the data for a givenneighborhood, city, metropolitan area, state, region, or country.

In an embodiment, the data path shown in FIGS. 3-4, beginning at MTCdevice 301, through the H-LTE-MTC gateway 232, Home eNode B 260 and HGW401, and ending at the data center 410, is a secure data path dedicatedto MTC data (that is, separate from HTC data and generated only byrecognized and approved devices).

FIG. 5 is a flowchart depicting an illustrative embodiment of a method500 used in portions of the system described in FIGS. 1-4. In step 502,a data packet generated by a device within residence 201 is received atthe H-LTE-MTC gateway. The gateway compares the device identifier on thedata packet with the list of MTC source device identifiers (step 504).If the sending device is found on the list (step 506), the gatewaycollects the data and optionally adds a tag to the data (step 510). Ifthe sending device is not a listed MTC sensor for the residence, thegateway can determine (step 507) whether a new sensor is to be added(step 508). In an embodiment, this can be done by consulting an updatelog at the gateway containing identifiers for recently installedsensors.

The data collected by the H-LTE-MTC gateway is transmitted to thededicated Home eNB device on the access network (step 512), and from theaccess network to the HGW on the core network (step 514). The MTC datais aggregated at the HGW and transmitted to the residential Data Center(step 516). The Data Center (which may be thought of as a “Big Data”configuration) analyzes and indexes the data to make it accessible (step518).

While for purposes of simplicity of explanation, the respectiveprocesses are shown and described as a series of blocks in FIG. 5, it isto be understood and appreciated that the claimed subject matter is notlimited by the order of the blocks, as some blocks may occur indifferent orders and/or concurrently with other blocks from what isdepicted and described herein. Moreover, not all illustrated blocks maybe required to implement the methods described herein.

It will be appreciated that the collection, transmission and analysis ofMTC data can be performed in commercial environments similarly toresidential environments. In particular embodiments, a commercialbuilding can have multiple Commercial LTE MTC gateways (C-LTE-MTCgateways) dedicated to specific types of data sensors or specificportions of the building. For example, a commercial facility can includean MTC device including a sensor for detecting a release of a chemicalmaterial or nuclear radiation. In further embodiments, commercial MTCdata is routed along a secure data path separate from the data path forresidential MTC data.

FIG. 6 depicts an illustrative embodiment of an architecture 600 for anetwork for interacting with mobile communication devices and/or IoTdevices. According to an embodiment of the disclosure, one or moremobile devices 616 and IoT devices 618 can connect with one or more ofthe networks shown in FIG. 6. Mobile devices 616 may represent a varietyof technologies (phones, tablets, etc.) and may have an end-to-endconnection established with either the Public Switched Telephone Network(PSTN) 660, in the case of voice traffic, or an internet protocolnetwork (Internet) 602, in the case of data traffic. The architecturecan include a Global System for Mobile (GSM) network 620, a 3G network630, and/or a Long Term Evolution (LTE) network 640. In particular, LTEspecifications define an all-internet protocol architecture with voiceover internet protocol (VoIP).

FIG. 6 also illustrates a device 615 accessing the network through abroadband connection 612 to an Internet Service Provider (ISP) 603. Anyof devices 615-616, coupled to a computing device (e.g. a server) of theISP, can comprise a processing system including a processor, and amemory that stores executable instructions that, when executed by theprocessing system, facilitate performance of operations. The operationscan include receiving data from a machine-type communication (MTC)device located at a premises, where the device and a plurality of MTCdevices are located at the premises; determining an identifier for theMTC device; comparing the identifier with a list of identifiersaccessible to the device; and, responsive to determining that the MTCdevice is a listed device based on the comparing, transmitting the datato a first network element remote from the premises; the first networkelement can comprise a femtocell. In addition, the processing systemdoes not receive data from user communication devices at the premisesgenerating human traffic communications (HTC); the first network elementdoes not receive HTC; and the first network element transmits the datato a second network element for aggregation and subsequent transmissionto a cloud data facility comprising cloud storage. Furthermore, a datapath from the processing system to the first network element, from thefirst network element to the second network element, and from the secondnetwork element to the cloud data facility can comprise a secure datapath.

FIG. 7 schematically illustrates a communication system 700 in which oneor more embodiments of the subject disclosure may be implemented. MobileStation 701 may be one of, but not limited to, a cellular telephone, acellular telephone in combination with another electronic device or anyother wireless mobile communication device. According to an embodimentof the disclosure, Mobile Station 701 and/or User Equipment 702 cancommunicate with one or more of the systems shown in FIG. 7 usingcarrier aggregation.

Mobile Station 701 may communicate wirelessly with Base Station System(BSS) 710. BSS 710 contains a Base Station Controller (BSC) 711 and aBase Transceiver Station (BTS) 712. BSS 710 may include a single BSC711/BTS 712 pair (Base Station) or a system of BSC/BTS pairs which arepart of a larger network. BSS 710 is responsible for communicating withMobile Station 701 and may support one or more cells. BSS 710 isresponsible for handling cellular traffic and signaling between MobileStation 701 and Core Network 740. BSS 710 can perform functions thatinclude, but are not limited to, digital conversion of speech channels,allocation of channels to mobile devices, paging, andtransmission/reception of cellular signals.

Additionally, Mobile Station 701 may communicate wirelessly with RadioNetwork System (RNS) 720. RNS 720 contains a Radio Network Controller(RNC) 721 and one or more Node(s) B 722. RNS 720 may support one or morecells. RNS 720 may also include one or more RNC 721/Node B 722 pairs oralternatively a single RNC 721 may manage multiple Nodes B 722. RNS 720is responsible for communicating with Mobile Station 701 in itsgeographically defined area. RNC 721 is responsible for controlling theNode(s) B 722 that are connected to it and is a control element in aUMTS radio access network. RNC 721 can perform functions such as, butnot limited to, load control, packet scheduling, handover control,security functions, as well as controlling access by Mobile Station 701access to the Core Network (CN).

The evolved UMTS Terrestrial Radio Access Network (E-UTRAN) 730 is aradio access network that provides wireless data communications forMobile Station 701 and User Equipment 702. E-UTRAN 730 provides higherdata rates than traditional UMTS. It is part of the Long Term Evolution(LTE) upgrade for mobile networks; later releases meet the requirementsof the International Mobile Telecommunications (IMT) Advanced and arecommonly known as a 4G networks. E-UTRAN 730 may include a series oflogical network components such as E-UTRAN Node B (eNB) 731 and E-UTRANNode B (eNB) 732. E-UTRAN 730 may contain one or more eNBs. UserEquipment 702 may be any user device capable of connecting to E-UTRAN730 including, but not limited to, a personal computer, laptop, mobiledevice, wireless router, or other device capable of wirelessconnectivity to E-UTRAN 730. The improved performance of the E-UTRAN 730relative to a typical UMTS network allows for increased bandwidth,spectral efficiency, and functionality including, but not limited to,voice, high-speed applications, large data transfer and IPTV, whilestill allowing for full mobility.

An exemplary embodiment of a mobile data and communication service thatmay be implemented in the PLMN architecture described in FIG. 7 is theEnhanced Data rates for GSM Evolution (EDGE). EDGE is an enhancement forGPRS networks that implements an improved signal modulation scheme knownas 9-PSK (Phase Shift Keying). By increasing network utilization, EDGEmay achieve up to three times faster data rates as compared to a typicalGPRS network. EDGE may be implemented on any GSM network capable ofhosting a GPRS network, making it an ideal upgrade over GPRS since itmay provide increased functionality of existing network resources.Evolved EDGE networks are becoming standardized in later releases of theradio telecommunication standards, which provide for even greaterefficiency and peak data rates of up to 1 Mbit/s, while still allowingimplementation on existing GPRS-capable network infrastructure.

Mobile Station 701 may communicate with any or all of BSS 710, RNS 720,or E-UTRAN 730. In an illustrative system, each of BSS 710, RNS 720, andE-UTRAN 730 may provide Mobile Station 701 with access to Core Network740. The Core Network 740 may include of a series of devices that routedata and communications between end users. Core Network 740 may providenetwork service functions to users in the Circuit Switched (CS) domain,the Packet Switched (PS) domain or both. The CS domain refers toconnections in which dedicated network resources are allocated at thetime of connection establishment and then released when the connectionis terminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed or handled independently ofall other packets in the PS domain and does not require dedicatednetwork resources.

The Circuit Switched-Media Gateway Function (CS-MGW) 741 is part of CoreNetwork 740, and interacts with Visitor Location Register (VLR) andMobile-Services Switching Center (MSC) Server 760 and Gateway MSC Server761 in order to facilitate Core Network 740 resource control in the CSdomain. Functions of CS-MGW 741 include, but are not limited to, mediaconversion, bearer control, payload processing and other mobile networkprocessing such as handover or anchoring. CS-MGW 741 may receiveconnections to Mobile Station 701 through BSS 710, RNS 720 or both.

Serving GPRS Support Node (SGSN) 742 stores subscriber data regardingMobile Station 701 in order to facilitate network functionality. SGSN742 may store subscription information such as, but not limited to, theInternational Mobile Subscriber Identity (IMSI), temporary identities,or Packet Data Protocol (PDP) addresses. SGSN 742 may also storelocation information such as, but not limited to, the Gateway GPRSSupport Node (GGSN) 744 address for each GGSN where an active PDPexists. GGSN 744 may implement a location register function to storesubscriber data it receives from SGSN 742 such as subscription orlocation information.

Serving Gateway (S-GW) 743 is an interface which provides connectivitybetween E-UTRAN 730 and Core Network 740. Functions of S-GW 743 include,but are not limited to, packet routing, packet forwarding, transportlevel packet processing, event reporting to Policy and Charging RulesFunction (PCRF) 750, and mobility anchoring for inter-network mobility.PCRF 750 uses information gathered from S-GW 743, as well as othersources, to make applicable policy and charging decisions related todata flows, network resources and other network administrationfunctions. Packet Data Network Gateway (PDN-GW) 745 may provideuser-to-services connectivity functionality including, but not limitedto, network-wide mobility anchoring, bearer session anchoring andcontrol, and IP address allocation for PS domain connections.

Home Subscriber Server (HSS) 763 is a database for user information; HSS763 can store subscription data regarding Mobile Station 701 or UserEquipment 702 for handling calls or data sessions. Networks may containone HSS 763, or more if additional resources are required. Exemplarydata stored by HSS 763 include, but is not limited to, useridentification, numbering and addressing information, securityinformation, or location information. HSS 763 may also provide call orsession establishment procedures in both the PS and CS domains.

The VLR/MSC Server 760 can provide user location functionality. In anembodiment, when Mobile Station 701 enters a new network location, itbegins a registration procedure. A MSC Server for that locationtransfers the location information to the VLR for the area. A VLR andMSC Server may be located in the same computing environment, as is shownby VLR/MSC Server 760, or alternatively may be located in separatecomputing environments. A VLR may contain, but is not limited to, userinformation such as the IMSI, the Temporary Mobile Station Identity(TMSI), the Local Mobile Station Identity (LMSI), the last knownlocation of the mobile station, or the SGSN where the mobile station waspreviously registered. The MSC server may contain information such as,but not limited to, procedures for Mobile Station 701 registration orprocedures for handover of Mobile Station 701 to a different section ofthe Core Network 740. GMSC Server 761 may serve as a connection toalternate GMSC Servers for other mobile stations in larger networks.

Equipment Identity Register (EIR) 762 is a logical element which maystore the International Mobile Equipment Identities (IMEI) for MobileStation 701. In a typical embodiment, user equipment may be classifiedas either “white listed” or “black listed” depending on its status inthe network. In one embodiment, if Mobile Station 701 is stolen and putto use by an unauthorized user, it may be registered as “black listed”in EIR 762, preventing its use on the network. Mobility ManagementEntity (MME) 764 is a control node which may track Mobile Station 701 orUser Equipment 702 if the devices are idle. Additional functionality mayinclude the ability of MME 764 to contact an idle Mobile Station 701 orUser Equipment 702 if retransmission of a previous session is required.

Communication system 700 can be overlaid or operably coupled with system600. In particular, system 700 can comprise a processing systemincluding a processor that performs a method including receiving, by aprocessing system comprising a processor, data from a machine-typecommunication (MTC) device located at a premises, where the processingsystem, a plurality of human-type communication (HTC) devices and aplurality of MTC devices are located at the premises. The method canfurther include determining an identifier for the MTC device; comparingthe identifier with a list of identifiers accessible to the processingsystem; and, responsive to determining that the MTC device is a listeddevice based on the comparing, transmitting the data to a first networkelement remote from the premises. In addition, when performing themethod, the processing system does not receive data from the HTCdevices; the first network element does not receive HTC; and the firstnetwork element transmits the data to a second network element foraggregation and subsequent transmission to a cloud data facilitycomprising cloud storage. Furthermore, a data path from the processingsystem to the first network element, from the first network element tothe second network element, and from the second network element to thecloud data facility can include a secure path dedicated to data from theMTC device.

It is further noted that various terms used in the subject disclosurecan include features, methodologies, and/or fields that may be describedin whole or in part by standards bodies such as Third GenerationPartnership Project (3GPP). It is further noted that some or allembodiments of the subject disclosure may in whole or in part modify,supplement, or otherwise supersede final or proposed standards publishedand promulgated by 3GPP.

FIG. 8 depicts an illustrative embodiment of a web portal 802 of acommunication system 800. Communication system 800 can be overlaid oroperably coupled with the systems of FIGS. 6-7 as another representativeembodiment of systems 600-700. The web portal 802 can be used formanaging services of communication systems 600-700. A web page of theweb portal 802 can be accessed by a Uniform Resource Locator (URL) withan Internet browser using an Internet-capable communication device suchas those described in FIGS. 6-8. The web portal 802 can be configured,for example, to access a media processor and services managed therebysuch as a Digital Video Recorder (DVR), a Video on Demand (VoD) catalog,an Electronic Programming Guide (EPG), or a personal catalog (such aspersonal videos, pictures, audio recordings, etc.) stored at the mediaprocessor. The web portal 802 can also be used for provisioning variousservices on the communication devices 810, for example IMS services,Internet services, cellular phone services, IoT services, and so on. Inparticular, web portal 802 can be used to access and/or configure IoTdevices, and/or perform inventory management of IoT devices.

The web portal 802 can further be utilized to manage and provisionsoftware applications and to adapt these applications as may be desiredby subscribers and/or service providers of communication systems600-700. For instance, users of the services provided by servers insystems 600-700 can log into their on-line accounts and provision thoseservers with information to enable communication with devices describedin FIGS. 6-7, and so on. Service providers can log onto an administratoraccount to provision, monitor and/or maintain the systems 600-700 ofFIGS. 6-7.

FIG. 9 depicts an illustrative embodiment of a communication device 900.Communication device 900 can serve in whole or in part as anillustrative embodiment of the devices depicted in FIGS. 1-4 and can beconfigured to perform portions of method 500 of FIG. 5.

Communication device 900 can comprise a wireline and/or wirelesstransceiver 902 (herein transceiver 902), a user interface (UI) 904, apower supply 914, a location receiver 916, a motion sensor 918, anorientation sensor 920, and a controller 906 for managing operationsthereof. The transceiver 902 can support short-range or long-rangewireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, orcellular communication technologies, just to mention a few (Bluetooth®and ZigBee® are trademarks registered by the Bluetooth® Special InterestGroup and the ZigBee® Alliance, respectively). Cellular technologies caninclude, for example, CDMA-1X, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO,WiMAX, SDR, LTE, as well as other next generation wireless communicationtechnologies as they arise. The transceiver 902 can also be adapted tosupport circuit-switched wireline access technologies (such as PSTN),packet-switched wireline access technologies (such as TCP/IP, VoIP,etc.), and combinations thereof.

The UI 904 can include a depressible or touch-sensitive keypad 908 witha navigation mechanism such as a roller ball, a joystick, a mouse, or anavigation disk for manipulating operations of the communication device900. The keypad 908 can be an integral part of a housing assembly of thecommunication device 900 or an independent device operably coupledthereto by a tethered wireline interface (such as a USB cable) or awireless interface supporting for example Bluetooth®. The keypad 908 canrepresent a numeric keypad commonly used by phones, and/or a QWERTYkeypad with alphanumeric keys. The UI 904 can further include a display910 such as monochrome or color LCD (Liquid Crystal Display), OLED(Organic Light Emitting Diode) or other suitable display technology forconveying images to an end user of the communication device 900. In anembodiment where the display 910 is touch-sensitive, a portion or all ofthe keypad 908 can be presented by way of the display 910 withnavigation features.

The display 910 can use touch screen technology to also serve as a userinterface for detecting user input. As a touch screen display, thecommunication device 900 can be adapted to present a user interface withgraphical user interface (GUI) elements that can be selected by a userwith a touch of a finger. The touch screen display 910 can be equippedwith capacitive, resistive or other forms of sensing technology todetect how much surface area of a user's finger has been placed on aportion of the touch screen display. This sensing information can beused to control the manipulation of the GUI elements or other functionsof the user interface. The display 910 can be an integral part of thehousing assembly of the communication device 900 or an independentdevice communicatively coupled thereto by a tethered wireline interface(such as a cable) or a wireless interface.

The UI 904 can also include an audio system 912 that utilizes audiotechnology for conveying low volume audio (such as audio heard inproximity of a human ear) and high volume audio (such as speakerphonefor hands free operation). The audio system 912 can further include amicrophone for receiving audible signals of an end user. The audiosystem 912 can also be used for voice recognition applications. The UI904 can further include an image sensor 913 such as a charged coupleddevice (CCD) camera for capturing still or moving images.

The power supply 914 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and/or charging system technologies for supplying energyto the components of the communication device 900 to facilitatelong-range or short-range portable applications. Alternatively, or incombination, the charging system can utilize external power sources suchas DC power supplied over a physical interface such as a USB port orother suitable tethering technologies.

The location receiver 916 can utilize location technology such as aglobal positioning system (GPS) receiver capable of assisted GPS foridentifying a location of the communication device 900 based on signalsgenerated by a constellation of GPS satellites, which can be used forfacilitating location services such as navigation. The motion sensor 918can utilize motion sensing technology such as an accelerometer, agyroscope, or other suitable motion sensing technology to detect motionof the communication device 900 in three-dimensional space. Theorientation sensor 920 can utilize orientation sensing technology suchas a magnetometer to detect the orientation of the communication device900 (north, south, west, and east, as well as combined orientations indegrees, minutes, or other suitable orientation metrics).

The communication device 900 can use the transceiver 902 to alsodetermine a proximity to a cellular, WiFi, Bluetooth®, or other wirelessaccess points by sensing techniques such as utilizing a received signalstrength indicator (RSSI) and/or signal time of arrival (TOA) or time offlight (TOF) measurements. The controller 906 can utilize computingtechnologies such as a microprocessor, a digital signal processor (DSP),programmable gate arrays, application specific integrated circuits,and/or a video processor with associated storage memory such as Flash,ROM, RAM, SRAM, DRAM or other storage technologies for executingcomputer instructions, controlling, and processing data supplied by theaforementioned components of the communication device 900.

Other components not shown in FIG. 9 can be used in one or moreembodiments of the subject disclosure. For instance, the communicationdevice 900 can include a reset button (not shown). The reset button canbe used to reset the controller 906 of the communication device 900. Inyet another embodiment, the communication device 900 can also include afactory default setting button positioned, for example, below a smallhole in a housing assembly of the communication device 900 to force thecommunication device 900 to re-establish factory settings. In thisembodiment, a user can use a protruding object such as a pen or paperclip tip to reach into the hole and depress the default setting button.The communication device 900 can also include a slot for adding orremoving an identity module such as a Subscriber Identity Module (SIM)card. SIM cards can be used for identifying subscriber services,executing programs, storing subscriber data, and so forth.

The communication device 900 as described herein can operate with moreor fewer of the circuit components shown in FIG. 9. These variantembodiments can be used in one or more embodiments of the subjectdisclosure.

The communication device 900 can be adapted to perform the functions ofdevices of FIGS. 6 and/or 7. It will be appreciated that thecommunication device 900 can also represent other devices that canoperate in systems of FIGS. 1-4.

Upon reviewing the aforementioned embodiments, it would be evident to anartisan with ordinary skill in the art that said embodiments can bemodified, reduced, or enhanced without departing from the scope of theclaims described below. Other embodiments can be used in the subjectdisclosure.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeunidirectional and/or bidirectional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 10 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 1000 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as the H-LTE-MTC gateway, the C-LTE-MTC gateway,and other devices of FIGS. 1-4. In some embodiments, the machine may beconnected (e.g., using a network 1026) to other machines. In a networkeddeployment, the machine may operate in the capacity of a server or aclient user machine in a server-client user network environment, or as apeer machine in a peer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 1000 may include a processor (or controller) 1002(e.g., a central processing unit (CPU)), a graphics processing unit(GPU, or both), a main memory 1004 and a static memory 1006, whichcommunicate with each other via a bus 1008. The computer system 1000 mayfurther include a display unit 1010 (e.g., a liquid crystal display(LCD), a flat panel, or a solid state display). The computer system 1000may include an input device 1012 (e.g., a keyboard), a cursor controldevice 1014 (e.g., a mouse), a disk drive unit 1016, a signal generationdevice 1018 (e.g., a speaker or remote control) and a network interfacedevice 1020. In distributed environments, the embodiments described inthe subject disclosure can be adapted to utilize multiple display units1010 controlled by two or more computer systems 1000. In thisconfiguration, presentations described by the subject disclosure may inpart be shown in a first of the display units 1010, while the remainingportion is presented in a second of the display units 1010.

The disk drive unit 1016 may include a tangible computer-readablestorage medium 1022 on which is stored one or more sets of instructions(e.g., software 1024) embodying any one or more of the methods orfunctions described herein, including those methods illustrated above.The instructions 1024 may also reside, completely or at least partially,within the main memory 1004, the static memory 1006, and/or within theprocessor 1002 during execution thereof by the computer system 1000. Themain memory 1004 and the processor 1002 also may constitute tangiblecomputer-readable storage media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Application specific integrated circuits andprogrammable logic array can use downloadable instructions for executingstate machines and/or circuit configurations to implement embodiments ofthe subject disclosure. Applications that may include the apparatus andsystems of various embodiments broadly include a variety of electronicand computer systems. Some embodiments implement functions in two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexample system is applicable to software, firmware, and hardwareimplementations.

In accordance with various embodiments of the subject disclosure, theoperations or methods described herein are intended for operation assoftware programs or instructions running on or executed by a computerprocessor or other computing device, and which may include other formsof instructions manifested as a state machine implemented with logiccomponents in an application specific integrated circuit or fieldprogrammable gate array. Furthermore, software implementations (e.g.,software programs, instructions, etc.) including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. Distributedprocessing environments can include multiple processors in a singlemachine, single processors in multiple machines, and/or multipleprocessors in multiple machines. It is further noted that a computingdevice such as a processor, a controller, a state machine or othersuitable device for executing instructions to perform operations ormethods may perform such operations directly or indirectly by way of oneor more intermediate devices directed by the computing device.

While the tangible computer-readable storage medium 1022 is shown in anexample embodiment to be a single medium, the term “tangiblecomputer-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “tangible computer-readable storage medium” shallalso be taken to include any non-transitory medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of the methods ofthe subject disclosure. The term “non-transitory” as in a non-transitorycomputer-readable storage includes without limitation memories, drives,devices and anything tangible but not a signal per se.

The term “tangible computer-readable storage medium” shall accordinglybe taken to include, but not be limited to: solid-state memories such asa memory card or other package that houses one or more read-only(non-volatile) memories, random access memories, or other re-writable(volatile) memories, a magneto-optical or optical medium such as a diskor tape, or other tangible media which can be used to store information.Accordingly, the disclosure is considered to include any one or more ofa tangible computer-readable storage medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having essentiallythe same functions. Wireless standards for device detection (e.g.,RFID), short-range communications (e.g., Bluetooth®, WiFi, Zigbee), andlong-range communications (e.g., WiMAX, GSM, CDMA, LTE) can be used bycomputer system 1000. In one or more embodiments, information regardinguse of services can be generated including services being accessed,media consumption history, user preferences, and so forth. Thisinformation can be obtained by various methods including user input,detecting types of communications (e.g., video content vs. audiocontent), analysis of content streams, and so forth. The generating,obtaining and/or monitoring of this information can be responsive to anauthorization provided by the user.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Theexemplary embodiments can include combinations of features and/or stepsfrom multiple embodiments. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. Figuresare also merely representational and may not be drawn to scale. Certainproportions thereof may be exaggerated, while others may be minimized.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement which achieves thesame or similar purpose may be substituted for the embodiments describedor shown by the subject disclosure. The subject disclosure is intendedto cover any and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, can be used in the subject disclosure.For instance, one or more features from one or more embodiments can becombined with one or more features of one or more other embodiments. Inone or more embodiments, features that are positively recited can alsobe negatively recited and excluded from the embodiment with or withoutreplacement by another structural and/or functional feature. The stepsor functions described with respect to the embodiments of the subjectdisclosure can be performed in any order. The steps or functionsdescribed with respect to the embodiments of the subject disclosure canbe performed alone or in combination with other steps or functions ofthe subject disclosure, as well as from other embodiments or from othersteps that have not been described in the subject disclosure. Further,more than or less than all of the features described with respect to anembodiment can also be utilized.

Less than all of the steps or functions described with respect to theexemplary processes or methods can also be performed in one or more ofthe exemplary embodiments. Further, the use of numerical terms todescribe a device, component, step or function, such as first, second,third, and so forth, is not intended to describe an order or functionunless expressly stated so. The use of the terms first, second, thirdand so forth, is generally to distinguish between devices, components,steps or functions unless expressly stated otherwise. Additionally, oneor more devices or components described with respect to the exemplaryembodiments can facilitate one or more functions, where the facilitating(e.g., facilitating access or facilitating establishing a connection)can include less than every step needed to perform the function or caninclude all of the steps needed to perform the function.

In one or more embodiments, a processor (which can include a controlleror circuit) has been described that performs various functions. Itshould be understood that the processor can be multiple processors,which can include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The virtual processingenvironment may support one or more virtual machines representingcomputers, servers, or other computing devices. In such virtualmachines, components such as microprocessors and storage devices may bevirtualized or logically represented. The processor can include a statemachine, application specific integrated circuit, and/or programmablegate array including a Field PGA. In one or more embodiments, when aprocessor executes instructions to perform “operations”, this caninclude the processor performing the operations directly and/orfacilitating, directing, or cooperating with another device or componentto perform the operations.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. A gateway comprising: a processing systemincluding a processor; a memory that stores executable instructionsthat, when executed by the processing system, facilitate performance ofoperations, comprising: receiving, by the gateway, data from amachine-type communication (MTC) device; storing the data at the gatewaywith second data previously stored at the gateway, resulting in a bundleof data; and transmitting the bundle of data from the gateway to a firstnetwork element remote for provisioning to a cloud data facilitycomprising cloud storage, wherein the cloud data facility arranges thedata with third data of a second bundle of data based on the data andthe third data corresponding to respective instances of a first type ofsensor, and wherein the cloud data facility arranges the second datawith fourth data of the second bundle of data based on the second dataand the fourth data corresponding to respective instances of a secondtype of sensor that is different from the first type of sensor.
 2. Thegateway of claim 1, wherein the data is received from the MTC deviceaccording to a predetermined schedule.
 3. The gateway of claim 1,wherein the MTC device comprises an environmental sensor.
 4. The gatewayof claim 1, wherein the gateway and the MTC device are each located at apremises.
 5. The gateway of claim 4, wherein the premises comprise aresidence.
 6. The gateway of claim 5, wherein the MTC device transmitsdata within the residence at a power level less than 100 mW.
 7. Anon-transitory machine-readable storage medium, comprising executableinstructions that, when executed by a processing system including aprocessor, facilitate performance of operations, comprising: receiving,by the processing system, data from a machine-type communication (MTC)device located at premises, wherein the processing system, a pluralityof MTC devices, and a plurality of human traffic communication (HTC)devices are located at the premises; storing the data at the processingsystem; and transmitting the data with second data as a bundle forprovisioning to a cloud data facility comprising cloud storage, whereinthe cloud data facility arranges the data with third data of a secondbundle based on the data and the third data corresponding to respectiveinstances of a first type of sensor, and wherein the cloud data facilityarranges the second data with fourth data of the second bundle based onthe second data and the fourth data corresponding to respectiveinstances of a second type of sensor that is different from the firsttype of sensor.
 8. The non-transitory machine-readable storage medium ofclaim 7, wherein the premises comprise a residence, and wherein the MTCdevice comprises an environmental sensor.
 9. The non-transitorymachine-readable storage medium of claim 7, wherein the premisescomprise a commercial facility, and wherein the MTC device comprises asensor for detecting a release of a chemical material or nuclearradiation.
 10. The non-transitory machine-readable storage medium ofclaim 7, wherein the MTC device transmits data within the premises at apower level less than 100 mW.
 11. A method comprising: receiving, by aprocessing system comprising a processor, data from a machine-typecommunication (MTC) device; storing, by the processing system, the data;and transmitting, by the processing system, the data with second data asa bundle to a first network element for provisioning to a cloud datafacility comprising cloud storage, wherein the cloud data facilityarranges the data with third data of a second bundle based on the dataand the third data corresponding to respective instances of a first typeof sensor, and wherein the cloud data facility arranges the second datawith fourth data based on the second data and the fourth datacorresponding to respective instances of a second type of sensor that isdifferent from the first type of sensor.
 12. The method of claim 11,wherein the fourth data is included in the second bundle.
 13. The methodof claim 11, wherein the fourth data is included in a third bundle ofdata.
 14. The method of claim 11, further comprising: receiving, by theprocessing system, an identifier of the MTC device; and comparing, bythe processing system, the identifier of the MTC device with a list ofidentifiers accessible to the processing system.
 15. The method of claim14, wherein the identifier of the MTC device is received from the MTCdevice.
 16. The method of claim 14, further comprising: determining,based on the comparing, that the identifier of the MTC device isincluded in the list, wherein the storing of the data is based on thedetermining.
 17. The method of claim 11, further comprising: receiving,by the processing system, the second data from a second MTC device;receiving, by the processing system, fifth data from a third MTC device;receiving, by the processing system, sixth data from one of the MTCdevice, the second MTC device, and the third MTC device; andtransmitting, by the processing system, the fifth data and the sixthdata as a third bundle, wherein the bundle and the third bundle are of auniform size.
 18. The method of claim 11, wherein the processing systemcomprises a first gateway and a second gateway, wherein the receiving ofthe data from the MTC device comprises the first gateway receiving thedata and the second gateway not receiving the data, the method furthercomprising: receiving, by the second gateway, the second data, whereinthe first gateway does not receive the second data.
 19. The method ofclaim 11, wherein the cloud data facility obtains fifth data and sixthdata corresponding to respective instances of the first type of sensor,wherein the cloud data facility arranges the data, the third data, thefifth data and the sixth data in accordance with a geographicalhierarchy based on the data and the third data corresponding to a firstgeographical area and the fifth data and the sixth data corresponding toa second geographical area.
 20. The method of claim 19, wherein thesecond geographical area is different form the first geographical area.